-
Notifications
You must be signed in to change notification settings - Fork 5.2k
try enabling ALCTest in GCStress again. #117388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Re-enables the ALCTest unit test under GCStress by removing the flag that marked it as incompatible.
- Deleted the
<GCStressIncompatible>true</GCStressIncompatible>property to allow the test to run under GCStress. - Removed the accompanying comment that temporarily disabled GCStress support.
|
/azp run runtime-coreclr gcstress0x3-gcstress0xc |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Looks like the ALCTest is passing in the gcstress pipeline: https://helix.dot.net/api/jobs/69fc089e-cdde-4d81-a3eb-617da9772180/workitems/profiler.0.1/files/console.8131af21.log?api-version=2019-06-17. @mdh1418, can you please confirm so we can get it enabled again. Thx. |
mdh1418
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does look like the test passed on this CI run.
Just to note, the original failure seemed flakey, so unless somehow the underlying cause was fixed by some alternate change, it might just be reopened again later.
|
Ok, let's enable for now and determine if it fails again and we can investigate at that time. |
Fixes #106241